Method and apparatus for transmitting data through inter-eNB carrier aggregation in wireless communication system

ABSTRACT

The present invention relates to a method and an apparatus for transmitting data to user equipment through not only a current base station cell but also a neighboring base station cell via inter-eNB CA in a wireless communication system. A method for transmitting data though carrier aggregation in the wireless communication system, according to the present invention, comprises the steps of: a first base station transreceiving data with a terminal through at least two PDN connections; the first base station transmitting a carrier aggregation request message to a second base station for aggregating carriers, when the first base station determines to carry out inter-eNB carrier aggregation; the first base station receiving a carrier aggregation reply message from the second base station in response to the carrier aggregation request message; the first base station performing an RRC reconfiguration process with the terminal to notify to the terminal of the determination to perform the inter-eNB carrier aggregation; and the first base station transmitting a path change request message to a mobile management entity to correct a data transreceiving path, so that data on at least one PDN connection from among the PDN connections is transreceived through the second base station.

TECHNICAL FIELD

The present invention relates to a wireless communication system and, inparticular, to a data transmission method and apparatus of a UserEquipment (UE) capable of inter-evolved Node B (eNB) Carrier Aggregationfor use of neighboring eNBs as well as the current eNB. Also, thepresent invention relates to a method and apparatus for communicatingdata of a specific PDN connections through cells of a neighboring eNB orpico cells to provide in a better condition.

BACKGROUND ART

Mobile communication systems were developed to provide the subscriberswith voice communication services on the move. With the rapid advance oftechnologies, the mobile communication systems have evolved to supporthigh speed data communication services beyond the early voice-orientedservices. However, the limited resource and user requirements for higherspeed services in the current mobile communication system spur theevolution to more advanced mobile communication systems.

In the wireless communication system, a terminal connects to a networkvia a base station (hereinafter, the term ‘eNB’ is interchangeably usedtherewith) for data communication. However, since the bandwidth of theeNB is restrictive, it may not satisfy the service quality requirementsof the users.

There is therefore a need of a method for dispersing the data of aspecific Packet Data Network (PDN) connection to neighboring eNBs whiletransmitting some data of the PDN connection trough the current eNB tofacilitate providing the communication service.

Technical Problem

The present invention has been conceived to solve the above problem andaims to provide a method and apparatus of providing the communicationservice in a good quality for the respective PDN connections in such away of, when it is difficult for an eNB to guarantee a high enough datarate, transmitting the data occurring on a certain PDN connectionthrough neighboring eNBs.

Solution to Problem

In order to solve the above problems, the method of transmitting datausing inter-base station carrier aggregation in a wireless communicationsystem according to the present invention is characterized by moving abearer corresponding to a PDN connection served by a certain eNB to aneighboring cell. For this purpose, the method includes, checking, at anMME, whether the UE and the eNB supports inter-eNB Carrier Aggregation(CA) in the initial attach procedure, notifying the eNB of the inter-eNBCA availability, determining, when generating a PDN connection, whetherit is a PDN connection movable in the inter-eNB CA, marking the PDNconnection in order for the eNB to identify the corresponding PDNconnection, detecting, at the eNB (PCell), the inter-eNB CA necessity,sending, at the eNB (PCell), the information on the bearerscorresponding to the PDN connection to be moved to the neighboring eNB(SCell), and notifying this to the S-GW via the MME, and transmittingthe data on the PDN connection moved to the SCell via the eNB (SCell)instead of the eNB (PCell).

Another method proposed in the present invention includes detecting, ata PCell or an SCell, the difficult of maintaining the inter-eNB CA andmoving the bearer serving at the SCell back to the PCell.

Another method proposed in the present invention includes transmitting aencryption key for use in data communication through SCell, exchangingthe encryption key, and generating the encryption key.

Advantageous Effects of Invention

The present invention is advantageous in terms of facilitating datacommunication in such a way of transmitting, when the bandwidth of aneNB is not enough for guaranteeing the service quality, the data on aspecific PDN connection through a neighboring eNB (SCell).

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a structure of connections betweennodes of the wireless communication system and a process of providingdata communication between the nodes according to an embodiment of thepresent invention.

FIG. 2 is a signal flow diagram illustrating a data communicationprocedure through carrier aggregation according to an embodiment of thepresent invention.

FIG. 3 is a signal flow diagram illustrating a procedure of releasingthe inter-eNB CA configuration according to an embodiment of the presentinvention.

FIG. 4 is a signal flow diagram illustrating an AS key update procedureaccording to an embodiment of the present invention.

FIG. 5 is a signal flow diagram illustrating an AS Key update procedureaccording to another embodiment of the present invention.

MODE FOR THE INVENTION

Exemplary embodiments of the present invention are described withreference to the accompanying drawings in detail. Detailed descriptionof well-known functions and structures incorporated herein may beomitted to avoid obscuring the subject matter of the present invention.

The following description of the embodiment of the present inventionproposes a method and apparatus for moving the bearers corresponding tosome PDN connections that are served by an eNB to a neighbor eNB (SCell)in a wireless communication system.

FIG. 1 is a diagram illustrating a structure of connections betweennodes of the wireless communication system and a process of providingdata communication between the nodes according to an embodiment of thepresent invention.

In FIG. 1, it is assumed that a certain UE 110 uses Voice over LTE andhigh volume data transmission services simultaneously. According to anembodiment of the present invention, in such a case, if it is difficultfor the eNB A 120 to guarantee the quality requirement of the user, aneighboring eNB B 130 is responsible for the high volume datatransmission service while the eNB A is responsible for the Voice overLTE data transmission.

By dispersing the load of the eNB to neighboring eNBs as describedabove, it is possible to facilitate the data transmission.

In the following description of the embodiment of the present invention,the eNB A maintaining a RRC connection with the UE is referred to asPrimary Cell (PCell), and the eNB B which has no RRC connection butacquire the control information through the PCell is referred to asSecondary Cell (SCell).

FIG. 2 is a signal flow diagram illustrating a data communicationprocedure through carrier aggregation according to an embodiment of thepresent invention.

As shown in FIG. 2, the UE 210 establishes an RRC connection with theeNB (PCell) 220 at step S205.

The MME 250 checks whether the eNB (PCell) 220, the eNB (SCell), and theUE support inter-eNB CA in the UE's access procedure or prior theretoand notifies the eNB (PCell) 220 whether it is possible to perform theinter-eNB CA through an S1-AP message at step S210.

The MME 240 also determines whether there is a PDN connection movable inthe middle of inter-eNB CA, when generating the PDN connection, andstores a UE context including the identifiers indicating the bearers inorder for the eNB (PCell) 220 to identify the corresponding PDNconnection. The bearer identifier may include the information on whetherto move to a SCell and the information capable of allowing the eNB toidentify the bearer per PDN connection in the inter-eNB CA environment.

In the case that there are two PDN connections before performing theinter-eNB CA, the data communications on both the PDN connections areperformed through the eNB (PCell) 220 as shown in at step S215.

In the inter-eNB CA, the eNB (PCell) 220 becomes aware that it isconfigured that the bearers of PDN connection 1 are remained in thePCell and the bearers of PDN connection 2 move to a SCell.

Afterward, if it is determined to perform the inter-eNB CA, the eNB(PCell) 220 sends the eNB (SCell) 230 a CA request message at step S220.The CA request message may include IDs of the bearers moving to theSCell (i.e. Radio Bearer IDs), QoS of bearers, UE ID (e.g., S-TMSI),address of the serving gateway (GW) to be used by the SCell, uplinkServing GW TEIDs, data forwarding requirement indicator, forwardingrelated information, Packet Data Convergence Protocol (PDCP) status, UEsecurity capability notifying of security algorithm and the like, andK_eNB* generated for use at the eNB (SCell).

At this time, if the eNB (PCell) 220 and the eNB (SCell) 230 use thesame AS key, the newly generated K_eNB* may be used as K_eNB in the eNB(PCell) 220 as well as the eNB (SCell) 230.

A description is made of the method of generating the K_eNB* in detailhereinafter.

Upon receipt of the CA request message, the eNB (SCell) 230 transmits aCA response message to notify that the inter-eNB CA is prepared at stepS225. The CA response message may include the TEID in transmitting, atthe serving GW, the downlink data to the eNB (eNB_Scell DL TEIDs) andthe TEIDs for use in forwarding the UE ID (e.g., S-TMSI) and data (TEIDsfor data-forwarding).

Upon receipt of the CA response message, the eNB (PCell) 220 performsthe RRC reconfiguration procedure at step S230 to notify the UE of theconfiguration of the inter-eNB CA to the eNB (SCell) 230 throughsCellToAddModList.

In the RRC reconfiguration procedure, the RRC reconfiguration requestmessage may include # of Inter-eNB CA activations to prevent, when theeNB (PCell) 220 and the eNB (SCell) 230 use the same AS key, the AS keyused previously from being reused AS key of the eNB (SCell) 230. Uponreceipt of # of inter-eNB CA activations, the UE references the value ingenerating the K_eNB* which is identical with the K_eNB* to be used bythe eNB (PCell) 220. A description is made of the method of generatingK_eNB* in detail hereinafter.

In the case that the eNB (PCell) 220 and the eNB (SCell) 230 usedifferent AS keys, in order to prevent the AS key of the eNB (SCell) 230from matching a previously generated AS key, # of inter-eNB CAactivations or # of KeNB_Scell refresh may be included according to theAS key management method of the eNB (SCell) 230. The UE generates theK_eNB* by referencing this information. A description is made of themethod of generating the K_eNB* used by the eNB (SCell) 230 in detailhereinafter.

If a RRC reconfiguration complete message is received in the RRCreconfiguration procedure, the eNB (PCell) 220 fords the data to the eNB(SCell) at step S235.

Then the eNB (PCell) 220 sends the MME 240 a Path Switch Request messageat step S240. The Path Switch Request message may include an inter-eNBCA flag indicating the inter-eNB CA, an address of the eNB (SCell),TEIDs to be used by the serving GW in downlink (eNB_Scell DL TEIDs), andIDs of the bearers moving to the SCell (radio bearer IDs).

Upon receipt of the Path Switch Request message, the MME 240 sends theserving GW/PDN GW 250 a Modify Bearer Request message at step S245 tomodify the paths of the corresponding bearers.

The MME 240 calculates UE AMBR for the SCell (UE-AMBR_Scell) at stepS250, receives a Modify Bearer Response message at step S255, and sendsthe eNB (PCell) 220 a Path Switch Request Ack message including the UEAMBR (UE-AMBR_Scell) at step S260.

The eNB (PCell) 220 sends the eNB (SCell) 230 the UE AMBR for SCell(UE-AMBR_Scell) through a CA Response Ack message at step S265.Meanwhile, the eNB (PCell) 220 checks the bearers to be moved to the eNB(SCell) 230 and calculates the UE AMBR for the PCell (UE-AMBR Pcell) atstep S270. For example, the calculation may be conducted as UE-AMBRPcell=UE-AMBR−UE-AMBR_Scell.

If the inter-eNB CA is configured completely, the eNB (PCell) 220 or theeNB (SCell) 230 activates the inter-eNB CA through Activation MACControl Element (CE) at step S275, and the PDN connection 2 is used tocommunicate data with the UE via the eNB (SCell) 230 at step S280.

In order to deactivate the inter-eNB CA, the eNB (PCell) 220 or the eNB(SCell) 230 may transmit a Deactivation MAC CE to deactivate theinter-eNB CA at step S285.

FIG. 3 is a signal flow diagram illustrating a procedure of releasingthe inter-eNB CA configuration according to an embodiment of the presentinvention. In the following description, the inter-eNB CA configurationrelease method may be categorized into a method for the eNB (PCell) 220to release the inter-eNB CA configuration after notifying the eNB(SCell) 230 thereof and a method for releasing without notifyingthereof.

It is assumed that the PDN connection 1 is established for datacommunication via the eNB (PCell) 220 and the PDN connection 2 isestablished for data communication via the eNB (SCell) 230 at step S305.

If it is determined that the inter-eNB CA is not necessary anymore, theeNB (PCell) 220 releases the inter-eNB CA configuration at step S310.

First, a description is made of the method for the eNB (PCell) 220 tonotify the eNB (SCell) 230 of the release of the inter-eNB CAconfiguration and then release the inter-eNB CA configuration.

In order to accomplish this, the eNB (PCell) 220 sends the eNB (SCell)230 a CA Cancel Command message at step S315, the CA Cancel Commandmessage including a UE ID (e.g., S-TMSI), a data forwarding requirementindicator, a TEID for data forwarding, and radio bearer IDscorresponding to PDN connections of which inter-eNB CA is to bereleased.

Upon receipt of the CA Cancel Command message, the eNB (SCell) 230 sendsthe eNB (PCell) 220 a CA Cancel Response message at step S320, the CACancel Response message including PDCP status information for dataforwarding.

Then the eNB (SCell) 230 forwards the data to the eNB (PCell) 220 atstep S325 and performs a Path Switch procedure.

In the case of releasing the inter-eNB CA configuration withoutnotifying to the eNB (SCell) 230, steps S315 and S325 may be omitted andthe eNB (PCell) 220 may perform the path switch procedure to block thepath to the eNB (SCell) 230.

The eNB (PCell) 220 sends the MME 240 a Path Switch Request message toinitiate the path switch procedure at step S330. The Path Switch Requestmessage may include an inter-eNB CA flag indicating the inter-eNB CA andIDs of the radio bearers for which the eNB (PCell) 220 determines torelease the CA in response to the request from the eNB (SCell) 230(selected radio bearer IDs).

Upon receipt of the Path Switch Request message, the MME 240 sends theserving GW/PDN GW a Modify Bearer Request message to modify the datatransmission path to the eNB (SCell) 230 at step S335.

The MME 240 calculates the UE-AMBR (UE-AMBR_Scell) for the eNB (SCell)230 at step S340 and, if a Modify Bearer Response message is receivedfrom the serving GW at step S345, sends the eNB (PCell) 220 a PathSwitch Request ACK message including the UE-AMBR_Scell at step S350. TheeNB (PCell) 220 sends the eNB (SCell) 230 a CA Cancel Response ACKmessage including the UE-AMBR_Scell at step S355, and the eNB (SCell)230 erases the corresponding UE context at step S360.

The eNB (PCell) 220 calculates UE-AMBR Pcell based on the receivedUE-AMBR_Scell at step S365, and the eNB (PCell) 220 or the eNB (SCell)230 transmits a Deactivation MAC CE to deactivate the Inter-eNB CA atstep S370.

The eNB (PCell) 220 performs the RRC reconfiguration procedure to notifythe UE of the updated situation of the inter-eNB CA at step S375.

In the case that the inter-eNB CA associated with the radio bearer IDscorresponding to the PDN connection 2, the data communication for boththe PDN connections 1 and 2 is performed via the eNB (PCell) 220 at stepS380.

Although the description is directed to the case where the bearers areprocess per PDN connection, it is also possible to process the bearersindependently as well as per PDN connection.

In another embodiment of the present invention, a description is made ofthe method and apparatus for managing the AS security key in the casethat the inter-eNB CA is applied.

In the case that the inter-eNB CA is performed as described withreference to FIG. 2, the eNB (PCell) 220 generates K_eNB* for the ASsecurity Key to be used at the eNB (SCell) 230 and sends the eNB (SCell)230 a CA Request message including the K_eNB*.

Then the eNB (SCell) 230 configures the K_eNB* received from the eNB(PCell) 220 as K_eNB to be used at the eNB (SCell) 230 and generatesencryption and integrity protection AS Keys such as K_eNB_int andK_eNB_enc for use in communication with the UE.

Afterward, if it is necessary to update the AS key (e.g. K_eNB refreshand K_eNB rekeying), the eNB (SCell) 230 updates the AS Key according tothe procedure depicted in FIG. 4.

FIG. 4 is a signal flow diagram illustrating an AS key update procedureaccording to an embodiment of the present invention.

As shown in FIG. 4, if K_eNB refresh is required, the eNB (SCell) 230sends the eNB (PCell) 220 a K_eNB refresh request at step S405.

At this time, the eNB (PCell) 220 performs the key refresh procedure bytransmitting the RRC reconfiguration request message to the UE at stepS410.

According to another embodiment of the present invention, since the eNB(PCell) 220 knows the key refresh is required already, it may skip thesubsequent step S415.

After transmitting the K_eNB refresh request message or receiving aK_eNB refresh notification message at step S415, the eNB (SCell) 230step forwarding data temporarily for Key refresh at step S420.

If it becomes necessary to perform K_eNB refresh or K_eNB rekeying, stepS405 is omitted, and the eNB (PCell) 220 performs key refresh or keyrekeying with the UE and sends the UE an RRC reconfiguration requestmessage at step S410.

In order to notify the eNB (SCell) 230 that the AS key update is beingperformed, the eNB (PCell) 220 transmits a K_eNB update notificationmessage at step S415. Upon receipt of the K_eNB update notificationmessage, the eNB (SCell) 230 stop forwarding data temporarily for Keyrefresh at step S420.

The RRC reconfiguration request message may include a Next hop chainingcounter (NCC) or a # of inter-eNB CA activations with the current K_eNBused in generating the K_eNB* at the UE. In order to indicate the casewhere the newly generated K_eNB* is used at the eNB (SCell) 230, theK_eNB_Scell refresh flag may be included.

In the case that the newly generated K_eNB* is used in both the eNB(PCell) 220 and eNB (SCell) 230, it is not necessary to include theK_eNB_Scell refresh flag.

If the new AS key is generated, the eNB (PCell) 220 generates a K_eNB*for use at the eNB (SCell) 230 based on the AS key and sends the eNB(SCell) 230 a K_eNB update response message including the new K_eNB* atstep S430. At this time, the eNB (SCell) 230 use the received K_eNB* asthe K_eNB.

The new K_eNB is applied by the eNB (SCell) 230 since the receipt of theK_eNB update request message such that the UE and the eNB (SCell) 230use the new K_eNB.

The eNB (PCell) 220 may use the new K_eNB since the receipt of the RRCreconfiguration complete message at step S435.

In order to notify the start time of applying the new K_eNB, it is alsopossible for the eNB (SCell) 230 to send the UE a MAC CE such that theeNB (SCell) 230 and the UE start using the new K_eNB since the MAC CEtransmission/reception at step S440.

Another embodiment proposes a method and apparatus of managing AS Keythat can be used in updating the AS Key autonomously without receivingthe AS key from the eNB (SCell) 230 in the inter-eNB CA situation.

Even in this method, the AS key update, which is caused by the AS keychange at the eNB (PCell) 220, can be performed as described withreference to FIG. 4.

In the case that the inter-eNB CA is performed as described with FIG. 2,the eNB (PCell) 220 generates the K_eNB* for AS security Key at the eNB(SCell) 230 and sends the eNB (SCell) 230 a CA request message includingthe K_eNB*). Upon receipt of the K_eNB* from the eNB (PCell) 220, theeNB (SCell) 230 configures the K_eNB* as its K_eNB to generate theencryption and integrity protection AS Key such as K_eNB_int andK_eNB_enc based on the K_eNB for use in communication with the UE.

Afterward, if it is necessary to update the AS key (e.g. K_eNB refresh),the eNB (SCell) updates the SK key according to the procedure of FIG. 5.

FIG. 5 is a signal flow diagram illustrating an AS Key update procedureaccording to another embodiment of the present invention.

As shown in FIG. 5, if the K_eNB refresh is necessary, the eNB (SCell)230 sends the eNB (PCell) 220 a K_eNB refresh indication message at stepS505 and stops forwarding data temporarily at step S510.

Next, the eNB (SCell) 230 generates a new K_eNB* according to the legacyK_eNB* generation method as shown in table 1 and uses the newlygenerated K_eNB* as K_eNB.

Upon receipt of the K_eNB refresh indication message, the eNB (PCell)220 sends the UE the RRC reconfiguration request message to notify ofthe new AS key information at step S515.

The RRC reconfiguration request message may include at least one of anext hop chaining counter, a K_eNB_Scell refresh flag, and a number ofinter-eNB CAs with current K_eNB for use in generating K_eNB* (# ofK_eNB_Scell refresh).

If an RRC reconfiguration complete message is received at step S520, theeNB (PCell) 220 sends the eNB (SCell) 230 a K_eNB update acknowledgementmessage to notify that the AS key update of the eNB (SCell) 230 to theUE at step S525. Upon receipt of the K_eNB update acknowledgementmessage, the eNB (SCell) 230 starts using the new K_eNB.

The eNB (SCell) 230 starts using the new K_eNB since receipt of theK_eNB update acknowledgement message, and the UE starts using the newK_eNB since the transmission of the RRC reconfiguration message at stepS520 such that the data forwarding is performed with the new K_eNB atstep S530.

In order to notify the new K_eNB application start time, it is alsopossible for the eNB (SCell) 230 to send the UE a MAC CE such that theeNB (SCell) 230 and the UE use the new K_eNB since the MAC CEtransmission/reception at step S535.

Table 1 shows a method of generating a new K_eNB* in which the eNB(PCell) 220 generates the new K_eNB* to the eNB (SCell) 230.

In the case of applying the method of table 1, the new K_eNB* isgenerated by repeating the K_eNB* generation procedure as many as the #of inter-eNB CA activations or # of KeNB_Scell refreshes in order toprevent a previously generated K_eNB* from being reused.

The AS key generation method may be used in the case that the eNB(SCell) 230 generates the AS key autonomously without involvement of theeNB (PCell) 220.

If the eNB (PCell) 220 and the eNB (SCell) 230 use the same AS key, theK_eNB* generated newly with table 1 is used at the eNB (PCell) 220 andthe eNB (SCell) 230 (however, when configuring and activating theinter-eNB CA as in FIG. 2, if the UE and the eNB (PCell) 220 do notperform AS key refresh through the RRC reconfiguration procedure atprocess 6, the K_eNB which the eNB (PCell) 220 uses currently isconfigured as K_eNB* other than following table 1).

Otherwise if the eNB (PCell) 220 and the eNB (SCell) 230 use differentAS keys, the newly generated K_eNB* is used only at the eNB (SCell) 230.

TABLE 1 K_eNB* generation method in which PCell generate K_eNB* to SCell: New K_eNB* is generated by repeating the following Key generationprocedure as many as #inter-CA activations or #_KeNB SCell refreshK_eNB*=HMAC-SHA-256(K_eNB, s), S=FC ll P0 ll L0 ll P1 ll L1, whereFC=0x13 P0=PCI(target physical cell id) L0=length of PCI(i.e. 0x00 0x02)P1=EARFCN-DL(target physical cell downlink frequency) L1-length ofEARFCN-DL(i.e. 0x00 0x02)

Table 1 shows the K_eNB* generation method 1 in which the eNB (PCell)220 generates a new AS key and transmits it to the eNB (SCell) 230.

Table 2 shows another method of generating a new K_eNB* in which the eNB(PCell) 220 generates the new K_eNB* and transmits it to the eNB (SCell)230.

In the case of applying the method of table 2, the new K_eNB* isgenerated in consideration of the # of inter-eNB CA activations or # ofKeNB_Scell refreshes to prevent a previously generated K_eNB* is notreused. The AS key generation method may be used in the case that theeNB (SCell) 230 generate the AS key autonomously without involvement ofthe eNB (pSCell) 220.

If the eNB (PCell) 220 and the eNB (SCell) 230 use the same AS key, theK_eNB* generated newly with table 2 is used at the eNB (PCell) 220 andthe eNB. Otherwise if the eNB (PCell) 220 and the eNB (SCell) 230 usedifferent AS keys, the newly generated K_eNB* is used only at the eNB(SCell) 230.

Table 2 shows a new K_eNB* generation method in consideration of the #of inter-eNB CA activations or # of KeNB_Scell refreshes to prevent apreviously generated K_eNB* is not reused when the eNB (PCell) 220 andthe eNB (SCell) 230 use different AS keys in which the new K_eNB* isgenerated using the K_eNB used by the eNB (PCell) 220 and transmitted tothe eNB (SCell) 230.

TABLE 2 K_eNB* generation method in which eNB (PCell) generate K_eNB* toSCell (considering # of inter-CA activations or # of KeNB_Scell refresh)K_eNB*=HMAC-SHA-256(K_eNB, s), S=FC ll P0 ll L0 ll P1 ll L1 ll P2 ll L2,where FC=unused FC allocation (14, 1C~1F) P0=PCI(target physical cellid) L0=length of PCI(i.e. 0x00 0x02) P1=EARFCN-DL(target physical celldownlink frequency) L1=length of EARFCN-DL(i.e. 0x00 0x02)P2=NHKD-Scell(Number of horizontal key derivation w.r.t the K_eNB inScell) L2=length of NHKD-Scell(i.e. 0x00 0x01)

Table 2 shows the K_eNB* generation method in which the eNB (PCell) 220generates a new AS key and sends it to the eNB (SCell) 230 (considering# of inter-eNB CA activations or # of KeNB_Scell refresh).

Although various embodiments of the present disclosure have beendescribed using specific terms, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense in order tohelp understand the present invention. It is obvious to those skilled inthe art that various modifications and changes can be made theretowithout departing from the broader spirit and scope of the invention.

For example, each of the eNB (PCell), the eNB (SCell), and the UE mayinclude a transceiver for transmitting/receiving signals and acontroller for performing the functions according to above describedembodiments of the present invention.

For example, the eNB (PCell) may include a transceiver fortransmitting/receiving signals and a controller. In this case, thecontroller may control to transmit and received data to and from the UEthrough at least two Packet Data Network (PDN) connections. Thecontroller may control sending a CA request to the second eNB whichparticipates in the CA when the inter-eNB CA is determined and receivinga CA response message from the second eNB in response to the CA requestmessage. The controller also may control performing the RRCreconfiguration procedure with the UE to notify the UE of the inter-eNBCA determination, transmit a path switch request message to the MME toswitch a path such that the data of at least one of PDN connections aretransmitted/received via the second eNB.

Likewise, the controller of each of the eNB (SCell) and the UE may beconfigured to perform the functions described in the above embodimentsof the present invention.

The invention claimed is:
 1. A method by a first base station in awireless communication system, the method comprising: transmitting, to asecond base station, a first message including information on at leastone bearer for which inter-base station carrier aggregation isconfigured; receiving, from the second base station, a second messageincluding configuration information for the at least one bearer inresponse to the first message; transmitting, to a terminal, a thirdmessage including the configuration information for the at least onebearer; and transmitting, to a mobility management entity, a fourthmessage for requesting modification of configuration for the at leastone bearer.
 2. The method of claim 1, further comprising transmitting,to the second base station, a fifth message to release the inter-basestation carrier aggregation.
 3. The method of claim 1, wherein the firstmessage comprises at least one of: an ID of the at least one bearermoving to the second base station, QoS of bearers, a terminalidentifier, an address of a serving gateway (GW) to be used by thesecond base station, an uplink serving gateway identifier, a dataforwarding determination indicator, a forwarding-related information,packet data convergence protocol (PDCP) status, terminal securitycapability notifying of security algorithm, or a key generated for useat the second base station.
 4. The method of claim 1, wherein the fourthmessage comprises at least one of: a flag indicating inter-base stationcarrier aggregation, an address of the second base station, informationfor use by a serving gateway in downlink, or an identifier of a bearermoving to the second base station.
 5. The method of claim 1, furthercomprising: receiving a key refresh request message from the second basestation; generating a new key information for refreshing the key in useaccording to the key refresh request; and transmitting the new keyinformation to the second base station.
 6. The method of claim 1,further comprising stopping data forwarding after receipt of a keyrefresh request message.
 7. A first base station in a wirelesscommunication system, the first base station comprising: a transceiverconfigured to transmit and receive signals; and a controller configuredto: transmit, to a second base station, a first message includinginformation on at least one bearer for which inter-base station carrieraggregation is configured, receive, from the second base station, asecond message including configuration information for the at least onebearer in response to the first message, transmit, to a terminal, athird message including the configuration information for the at leastone bearer, and transmit, to a mobility management entity, a fourthmessage for requesting modification of configuration for the at leastone bearer.
 8. The first base station of claim 7, wherein the controlleris further configured to control transmitting, to the second basestation, a fifth message to release the inter-base station carrieraggregation.
 9. The first base station of claim 7, wherein the firstmessage comprises at least one of: an ID of the at least one bearermoving to the second base station, QoS of bearers, a terminalidentifier, an address of a serving gateway (GW) to be used by thesecond base station, an uplink serving gateway identifier, a dataforwarding determination indicator, a forwarding-related information,packet data convergence protocol (PDCP) status, terminal securitycapability notifying of security algorithm, or a key generated for useat the second base station.
 10. The first base station of claim 7,wherein the fourth message comprises at least one of: a flag indicatinginter-base station carrier aggregation, an address of the second basestation, information for use by a serving gateway in downlink, or anidentifier of a bearer moving to the second base station.
 11. The firstbase station of claim 7, wherein the controller is further configuredto: control receiving a key refresh request message from the second basestation, generate a new key information for refreshing the key in useaccording to the key refresh request, and transmit the new keyinformation to the second base station.
 12. The first base station ofclaim 7, wherein the controller is further configured to controlstopping data forwarding after receipt of a key refresh request message.